Controlling and using virtual universe wish lists

ABSTRACT

Described herein are processes and devices that control and use virtual universe wish lists. One of the devices described is a virtual wish list device. The virtual wish list device determines an item in a virtual universe that is a desired by an avatar. The virtual wish list device designates the item as a desired item in a wish list. The wish list may be stored in the avatar&#39;s virtual universe inventory. The wish list device determines details about the desired item, such as whether the item is desired in the virtual universe or in the real world. The wish list device stores the details about the desired item in the wish list. The virtual wish list device may use the details to conduct transactions related to the desired item.

BACKGROUND

1. Technical Field

Embodiments of the inventive subject matter relate generally to virtualuniverse systems, and more particularly to controlling and using virtualuniverse wish lists.

2. Background Art

Virtual universe applications allow people to socialize and interact ina virtual universe. A virtual universe (“VU”) is a computer-basedsimulated environment intended for its residents to traverse, inhabit,and interact through the use of avatars. Many VUs are represented using3-D graphics and landscapes, and are populated by many thousands ofusers, known as “residents.” Other terms for VUs include “metaverses”and “3D Internet.”

SUMMARY

Described herein are processes and devices that control and use virtualuniverse wish lists. One of the devices described is a virtual wish listdevice. The virtual wish list device determines an item in a virtualuniverse that is a desired by an avatar. The virtual wish list devicedesignates the item as a desired item in a wish list. The wish list maybe stored in the avatar's virtual universe inventory. The wish listdevice determines details about the desired item, such as whether theitem is desired in the virtual universe or in the real world. The wishlist device stores the details about the desired item in the wish list.The virtual wish list device may use the details to conduct transactionsrelated to the desired item.

BRIEF DESCRIPTION OF THE FIGURES

The present embodiments may be better understood, and numerous objects,features, and advantages made apparent to those skilled in the art byreferencing the accompanying drawings.

FIG. 1 is an illustration of an example virtual wish list device 102within an operating environment 100.

FIG. 2 is an example illustration of preparing and tracking virtualitems for use with virtual wish lists.

FIG. 3 is an illustration of an example virtual wish list devicearchitecture 300.

FIG. 4 is an example flow diagram 400 illustrating controlling virtualitems in a virtual wish list.

FIG. 5 is an example flow diagram 500 illustrating using virtual wishlist details.

FIG. 6 is an illustration of an example virtual wish list device 602 ona network 600.

FIG. 7 is an illustration of an example virtual wish list devicecomputer system 700.

DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The description that follows includes exemplary systems, methods,techniques, instruction sequences and computer program products thatembody techniques of embodiments of the invention(s). However, it isunderstood that the described embodiments of the invention(s) may bepracticed without these specific details. For instance, althoughexamples refer to storing item details in a wish list in the virtualuniverse, such as on virtual universe servers, other examples may storeitem details outside of the virtual universe, such as on client devices.In other instances, well-known instruction instances, protocols,structures and techniques have not been shown in detail in order not toobfuscate the description.

Introduction

VU environments have become increasingly popular for all types ofentertainment and commerce. Avatars in the VU represent agents, or reallife users, with desires for items and services. A VU user's avatar mayspend a good deal of time residing in the VU. Consequently, a VU couldgreatly benefit from devices that would assist the VU avatars to tracktheir desires for items and services without having to leave the VU.However, conventional VU's lack automated abilities to allow users toexpress desires, or wishes, for goods and services from within a virtualuniverse, and to obtain those goods and services. FIG. 1 shows how avirtual wish list device may work within a VU to create and controlvirtual wish lists.

FIG. 1 is an illustration of an example virtual wish list device 102within an operating environment 100. In FIG. 1, a virtual wish listdevice 102 is connected to a communication network 122. Also connectedto the communication network 122 are one or more client devices 110, 111configured to provide access to a virtual universe 101. A server 128 isalso connected to the communication network 122. In this illustration,the server 128 hosts the virtual universe 101. A database 130 isconnected to the server 128. The database 130 stores information aboutvirtual universe inventories, wish lists, etc. Of course, theinformation may be stored on the server 128, and perhaps servers inaddition to or instead of a standalone database.

The virtual universe 101 includes various graphical objects 108 (e.g.,buildings, avatars, vehicles, etc.) that make up the virtual universe101. One such graphical object includes a virtual item 103. A virtualitem, for example, includes any object in the virtual universe that hasa universally unique identifier (UUID). The virtual item 103 is an itemthat an avatar 104, representing a user account, agent, inhabitant, orresident, desires to possess. The avatar 104 may desire to possess theitem in different ways. For example, the avatar 104 may desire topossess the actual object displayed in the virtual universe 101 thatcomprises the virtual item 103. Alternatively, the avatar 104 may desireto possess a copy of the virtual item 103 in the virtual universe 101.Further, the avatar 104 may desire to possess a real-world item that thevirtual item 103 represents.

The virtual wish list device 102, in stage “1”, determines that the item103 is desired by the avatar 104. For example, the virtual wish listdevice 102 detects when the avatar 104 selects the virtual item 103. Thevirtual wish list device 102 processes an operation, initiated by theavatar 104, such as a mouse right-click operation, to present an optionsscreen 105. The virtual wish list device 102 recognizes when the avatar104 selects an option 106 on the options screen 105. By selecting theoption 106, the avatar 104 indicates a desire to place information, ordetails, about the virtual item 103 on a virtual wish list 112. Thevirtual wish list device 102 also presents a box 107 for the avatar 104to notate something specific that is desired. For example, the avatar104 may notate desired characteristics (e.g., color, type, etc.) aboutthe virtual item 103 or desired characteristics that are different fromthe virtual item 103. For another example, if the virtual item 103 isrepresentative of a real-world item, the avatar 104 may notate thedesired or undesired characteristics (e.g., condition, age, tax,shipping details, etc.) about the real-world item represented by thevirtual item 103.

The virtual wish list device 102, in stage “2”, designates the virtualitem 103 on a virtual wish list 112. The virtual wish list device 102may create the wish list 112 and display it in a virtual inventory ofthe avatar 104. The virtual wish list device 102 designates the virtualitem 103, for example, by recording on the wish list 112 details aboutthe virtual item 103, the avatar 104, and the operating environment 100.Details about the virtual item 103 may include information 114 thatidentifies the virtual item 103 as well as information 115 that theavatar 104 specifies or notates about the virtual item 103. Detailsabout the avatar 104 may include information 113, such as an image ofthe avatar and the avatar's name, or even metadata 118 (e.g.,demographics, and address, etc.) specifically referring to the agentassociated with the avatar 104. The metadata 118 may be hidden from viewon the virtual wish list 112 as depicted in FIG. 1, but still isavailable for extraction from the virtual wish list 112. Details aboutthe operating environment 100 may include information 119, whichindicates the date that the virtual wish list device 102 designated thevirtual item 103 in the virtual wish list 112. Other examples ofoperating environment information include indication of any securityviolations around the time the virtual item 103 was designated in thevirtual wish list 112, geographic location of the virtual wish listdevice 102, the date that the virtual wish list device 102 willautomatically remove the virtual item 103 from the virtual wish list112, etc.

Designating the virtual item 103 may also include analyzing the virtualuniverse 101 for details that may pertain to the virtual item 103. Forexample, the virtual wish list device 102 could read from the database130 to obtain details that had been previously stored about the virtualitem 103, such as a manufacturer of the virtual item 103. The virtualwish list device 102 may then analyze the details from the database 130,for example, to and search for and provide a location link 127 to amerchant that offers for sale instances of the virtual item 103, orother items made by the manufacturer.

The virtual wish list device 102, in stage “3”, accesses the virtualwish list 112 for item details. For example, a second avatar 109 that isinterested in viewing the first avatar's 104 desired items could viewthe wish list 112 within the virtual universe 101 using a client device111. The virtual wish list device 102 could provide access to the secondavatar 109 and other avatars and user accounts that the first avatar 104authorizes to view the wish list 112.

The virtual wish list device 102, in stage “4”, conducts transactionsregarding the item or details. For example, the virtual wish list device102 could transport the second avatar 109 to the location of a merchant,such as by selecting the location link 127. Further, the virtual wishlist device 102 may present buttons 116 that allow the second avatar 109to buy an instance of the item from the merchant. The avatar 109 canthen give the purchased instance of the item to first avatar 104.

The virtual wish list device 102, in stage “5”, extracts and usesdetails and metadata available from the virtual wish list 112. Forexample, a virtual wish list device 102 mines details from the virtualwish list 112, or other wish lists stored in the server 128 or database130. The virtual wish list device 102 provides the details to asubscribed computer 117. The virtual wish list device 102 analyzes thedata for various purposes, such as for marketing or market research. Forinstance, the virtual wish list device 102 can analyze the metadataand/or details of a particular item designated in multiple wish lists todetermine a number of avatars that desire the item, popularity ofvariable characteristics of the item, etc. As another example, thevirtual wish list device 102 could generate an electronic coupon orvoucher for the virtual item 103 and attach it to an email message 126.The virtual wish list device 102 could print coupons and vouchers with aprinter 125. The virtual wish list device 102 could send the electroniccoupons or vouchers to the first avatar 104, the second avatar 109, orto agents associated with the avatars 104, 109.

Example Operating Environments

This section describes example operating environments and networks andpresents structural aspects of some embodiments. More specifically, thissection includes discussion about virtual wish list device operatingenvironments and virtual wish list device architectures.

Example of Preparing And Tracking Virtual Items For Use With VirtualWish Lists

FIG. 2 is an example illustration of preparing and tracking virtualitems for use with virtual wish lists. In FIG. 2, an operatingenvironment 200 includes a virtual wish list device 202 connected to acommunication network 222. Also connected to the communication network122 is a client device 210 configured to provide access to a virtualuniverse 201. A server 228 is also connected to the communicationnetwork 122. The server 228 hosts the virtual universe 101. A database230 is connected to the server 128. The database 230 stores informationabout virtual universe inventories, wish lists, etc.

Within the virtual universe are one or more virtual items (“items”),item “A” 204, item “B” 208, and item “C” 214. Item A 204 represents agraphical object that has been created for use in the virtual universe,for example, a graphical representation of a portable digital assistant(PDA). Item A 204 may be utilized in the virtual universe 201 by anavatar. Item A 204 has identifying information, or details 206. Thesedetails 206 are stored in the database 230. One of the details 206includes a universally unique identifier (UUID) to identify the itemwithin the virtual universe 201. Item A 204 has a corresponding entry232 in the database 230 with a unique database identification key, likea system identification number (“system ID”), to indicate the uniqueentry in the database 230. The system ID may match the UUID, or it maybe different. The virtual wish list device 202 uses the system ID tolocate the database entry and find details about item A 204, such as themanufacturer, the color, the model number, etc. The virtual wish listdevice 202 may clone item A 204 to create item B 208, which is aninstance of item A 204. As part of the cloning process, the virtual wishlist device 202 may copy a unique identification number from item A 204,such as the UUID or the system ID, and store it as details 212 relatedto item B 208. The virtual wish list device 202 may utilize the uniqueidentification number of the originating object, item A 204, to searchand find details pertaining to item A 204 within the database 230.Details and/or metadata about the item A 204 may also be copied into theentry 212 for item B 208 as part of the cloning process.

In some examples, however, an item exists in the virtual universe, likeitem C 214, which contains very few details 216. The item C 214 has aUUID, but there is no unique identifier number that may tie the clonedobject back to a parent object. Consequently, the item C 214 may lacksufficient identifying information for the virtual wish list device 202to properly designate item C 214 in a virtual wish list, or to storeother details in the virtual wish list, like a location where aninstance of the item could be purchased. Thus, in such an example, thevirtual wish list device 202 searches the virtual universe 201,including the database 230, or other devices like the server 228, usingwhat few details 216 it does have access to for item C 204. Further, thevirtual wish list 202 may present a console 218 with a search field 220for an agent to enter search criteria about item C 214. The virtual wishlist device 202 processes the search and produces results 224. Theresults 224 contain a list of possible entries found in the database 230that match the search criteria, such as entries 232 and 234 of thedatabase 230. The virtual wish list device 202 produces links 226 that,when selected, provide additional information about the results 224. Thevirtual wish list device 202 selects the link 226 that most closelyresembles item C 214, such as per the request of an avatar. The virtualwish list device 202 presents a selection box 227 and an update button228, to select the proper result and update details for item C 214. Oncethe update button 228 is selected, the virtual wish list device 202updates the details 216 for item C 214. In FIG. 2, the link 226corresponds to the entry 232, which has details for the item A 204. Inthis example, the virtual wish list device 202 determines that the entry232 has details for the item A 204. The virtual wish list device 202determines that the matching entry 232 corresponds to the item A 204(e.g., the virtual wish list device determines the UUID of the item A204 with the SYSID in the entry 232, which happen to be the same in thisexample illustration). The virtual wish list device 202 then associatesat least the UUID of the item A 204 with item C 214. Various techniquescan be employed to associate information of different items or instancesof an item. For example, the virtual wish list device 202 can augmentthe entry 216 with one or more fields to indicate some or all of thedetails of the item A 204. In another embodiment, the virtual wish listdevice 202 can create or update a reference in the entry 216 to theentry 232 and/or the entry 206. In FIG. 2, the virtual wish list device202 records the determined UUID into a field “ORIGINATING UUID” of theentry 216. Updating the entry 216 allows visibility of a relationshipbetween the item A 204 and the item C 214 for various purposes (e.g.,transaction processing for item C 214, market research, data mining,etc.).

Example Virtual Wish List Device Architecture

FIG. 3 is an illustration of an example virtual wish list devicearchitecture 300. In FIG. 3, the virtual wish list device architecture300 includes a virtual wish list device 302 configured to interface withsystems and networks 322.

The virtual wish list device architecture 300 may include a virtualinventory manager 310 to manage wish list information within an avatar'sinventory. The virtual inventory manager 310 may also control thelocation and movement of wish list items as they are purchased andtransferred. The virtual inventory manager 310 may access virtual wishlists in virtual inventories to access details about desired items onthe wish lists.

The virtual wish list device architecture 300 includes a virtual itemdesignator unit 312 configured to designate items in virtual wish lists.The virtual item designator unit 312 may select desired items and storeidentifying information about the virtual items on a virtual wish list.The virtual item designator unit 312 may also create virtual wish listsand place them where an avatar or agent may access it, such as in theavatar's virtual inventory.

The virtual wish list device architecture 300 includes a virtual wishlist data handler 314 configured to determine details about designateditems. The virtual wish list data handler 314 may analyze networkdevices, such as databases, to extract details to be used fordesignation and processing. The virtual wish list data handler 314 mayalso receive specified and notated details, provided by an avatar, andstore those details on a virtual wish list.

The virtual wish list device architecture 300 also includes a wish listdesignation rules store 316 configured to store rules regardingdesignation of items in a wish list in a virtual universe.

The virtual wish list device architecture 300 includes a virtual wishlist transactions processor 318 configured to process transactions usingdetails about designated items. The virtual wish list transactionsprocessor 318 may process transactions using details stored on a virtualwish list. Examples of transactions include moving items and avatars,purchasing items and gifting them, generating coupons, etc.

The virtual wish list device architecture 300 further includes a virtualuniverse authorization information store 320 configured to access andcontrol virtual universe accounts. For example, the virtual universeauthorization information store 320 may provide account identifiers thatauthorize access to virtual wish lists. The virtual universeauthorization information store 320 may store account settings thatindicate which avatars, accounts, businesses, etc., have access to anavatar's wish list.

Finally, the virtual wish list device architecture 300 includes acommunication interface 321 configured to facilitate communicationbetween the components of the virtual wish list device 302.

Each component shown in the virtual wish list device architecture 300 isshown as a separate and distinct element. However, some functionsperformed by one component could be performed by other components. Forexample, the virtual item designator unit 312 could also analyze anddetermine details about a virtual item similar to the virtual wish listdata handler 314. Further, the components shown may all be contained inthe virtual wish list device 302, but some, or all, may be included in,or performed by, other devices on the systems and networks 322. Inaddition, the virtual wish list device architecture 300 may beimplemented as software, hardware, any combination thereof, or otherforms of embodiments not listed.

Example Operations

This section describes operations associated with some embodiments ofthe invention. In the discussion below, the flow diagrams will bedescribed with reference to the block diagrams presented above. However,in some embodiments, the operations may be performed by logic notdescribed in the block diagrams.

In certain embodiments, the operations may be performed by executinginstructions residing on machine-readable media (e.g., software), whilein other embodiments, the operations may be performed by hardware and/orother logic (e.g., firmware). Moreover, some embodiments may performless than all the operations shown in any flow diagram.

FIG. 4 is an example flow diagram illustrating controlling virtual itemsin a virtual wish list. In FIG. 4, the flow 400 begins at processingblock 402, where a virtual wish list device prepares an item for wishlist designation in a virtual universe. One example of preparing an itemmay include assigning details to the item when it is first created inthe virtual universe. Details include identifying information about theitem, such as a universally unique identifier (UUID), a manufacturername for an item, a creation date, information about the item's virtualcharacteristics like color, size, location, etc. Thus, the virtual wishlist device may clone the item by copying details from the original itemand assigning them to the cloned item. The virtual wish list device usesthose details in conjunction with wish lists. When the virtual wish listdevice clones an item, it creates a new UUID, but also copies theoriginal UUID and stores the original UUID as a detail on the cloneditem. Consequently, the virtual wish list device may look up theoriginal item using the original UUID and obtain details when necessary.In cases where a cloned item already exists in a virtual universewithout a reference back to an original UUID, the virtual wish listdevice determines information about the cloned item, then searches thevirtual universe to find details about the original item. Further, thevirtual wish list device determines information about the cloned item byanalyzing the cloned item, such as to determine characteristics aboutthe item. The virtual wish list device also receives details about theitem from an observer, such as from an avatar or agent that describesthe item's characteristics as search criteria. The virtual wish listuses the search criteria to search virtual universe databases, or anyother network devices that might contain information on items. Once thevirtual wish list device obtains details about the cloned item, such asan original UUID, a manufacturer, etc., it stores or references thatinformation in conjunction with the item. Embodiments may also assign anindication of item type, class, and/or category to an item. Thisindication would carry over to clones until a clone is modified to adegree that it falls into a different category, class, or type. When anitem transitions into a different item class, type, or category, and isassigned a new indication, then the previous indication may be recordedas a predecessor class (type or category) indication. Embodiments maymaintain a history of predecessor indications.

The flow 400 continues at processing block 404, where the virtual wishlist device determines an item in a virtual universe that is desired byan avatar. For example, a virtual wish list device determines an item inthe virtual universe by selecting the item and determining that anavatar desires to place the virtual item on a virtual wish list. Forinstance, the virtual wish list device may detect when an avatar, amouse pointer, etc, touches an item in the virtual universe. The virtualwish list device may not be certain why the avatar has touched the item.Therefore, the virtual wish list device could present an options screenfor the avatar to indicate whether the avatar desires to place thevirtual item in a wish list. The virtual wish list device recognizesthat the avatar indicates a desire to place the item on the virtual wishlist. Any item within the virtual universe may be a potential wish listitem. For instance, a potential wish list item may be in a store, in theavatar's inventory, depicted in an advertisement, announced over a radiobroadcast in a virtual universe, on another avatar or elsewhere in thevirtual universe. An avatar may select items as part of normalinteraction in the virtual universe. For example, an avatar mayright-click on a musician and indicate that the song the musician issinging should be added to the avatar's wish list. The virtual wish listdevice could present a plurality of options of what the avatar desires(e.g., “desire mp3 of song?”, “desire album of artist?”, “desire ticketsto artist's upcoming performance?”, “Other?”). The virtual wish listdevice could also present a box for the avatar to notate somethingspecific that is desired. Potential wish list items may be items thatthe avatar doesn't possess in the virtual universe or outside thevirtual universe; items that the avatar already possesses in the virtualuniverse, but wants as a real-world copy of the item; items possessedoutside of the real world but desired in the virtual universe; or itemspossessed in either the virtual universe or real world, of which theavatar wants another copy. Further, potential wish list items may berepresentations of actual items, such as a listing in an advertisementor a catalog, of a virtual item.

The flow 400 continues at processing block 406, where the virtual wishlist device designates the item as a desired item in a virtual wishlist. The virtual wish list device determines identifying details aboutthe virtual item. Identifying details include any information that thevirtual wish list device may later use to identify the item from thewish list, such as the item's UUID, manufacturer, size, shape, color,image, etc. The virtual wish list device stores the identifying detailson the wish list. If a wish list does not exist for an avatar, thevirtual wish list device may create a wish list, such as within theavatar's inventory as a list of desired items, or “wishes”, that do notbelong to the inventory as an actual item, but that are desired. Thevirtual wish list device stores the identifying details in the virtualwish list by placing the identifying details as an entry on the wishlist. The virtual wish list may enumerate the item on the wish list tosegregate the item from other potential items on the wish list. In otherexamples, the virtual wish list device could store the wish list inother places other than the avatar's inventory, such as a separate listavailable to the avatar. In yet other examples, the virtual wish listcould store the wish list outside of the virtual universe (e.g., in afile format that a client application can read and/or modify, on a webserver that tracks wish list items, etc.).

The flow 400 continues at processing block 408, where the virtual wishlist device determines details about the desired item. For example, thevirtual wish list device displays an option screen to the avatar tonotate details about the avatar's wish or desire to possess the item.For example, the virtual wish list device captures details entered bythe avatar about whether the item is desired in the virtual universe, asa virtual item, or in the real world, as an actual item. The virtualwish list device captures other details that the avatar notates aboutwhat is desired, such as characteristics of the desired item, likecolor, type, description, etc. The virtual wish list device receives thenotated details and stores the notated details along with theidentifying details on the wish list. Notated details may include adegree, or ranking, of desirability, such as to what degree an avatardesires the item over other possible items on the wish list. Notateddetails may also include specifying specifics about the desired itemthat are not easily ascertainable. For example, a first avatar mightselect a body part on a second avatar, such as the second avatar's hair.However, only selecting the item does not provide enough detail for thevirtual wish list device to be clear about the first avatar desire aboutthe hair, so the first avatar would have to clarify the desire withnotes (e.g. wants the same hair style for the avatar, wants the samehair color for the avatar, wants a similar haircut in real world, etc.)Notated details may also include categories for the item as well as aset price that an avatar is willing to pay for the item and a quantityof an item. Noted details may also include contact information, such asa shipping address. In addition to determining notated details, thevirtual wish list device may also analyze the virtual item to determinenon-notated details, such as characteristics or categories of the item.Further, the virtual wish list device may automatically determine systemdetails. System details could include the date that an item isdesignated or details about the avatar, its associated user account, orany other information available to the virtual wish list device throughthe virtual universe network. Further, the virtual wish list maydetermine item account details, such as information stored in a databaseentry that is related to the item. For example, when the virtual wishlist device prepared the item, it determined item details and storedthem in a database. Thus, the virtual wish list device may refer to thedatabase entry for the item to determine additional details about theitem. The virtual wish list could reference an item's entry in thedatabase by referencing the original UUID. Further, the virtual wishlist device determines information about where to obtain the item. Forinstance, a manufacturer of the item may include a virtual “landmark” aspart of the item details to specify coordinates in the virtual universewhere the item may be purchased. The virtual wish list device may obtaininformation about the avatar's past history that could relate to theitem. For example, the virtual wish list device could analyze anavatar's purchasing history or association with manufacturers andsellers that might offer the item for sale. As a result, the virtualwish list device could utilize the historical information to direct theavatar, or others, to a provider of the item.

The flow 400 continues at processing block 410, where the virtual wishlist device stores the details on the virtual wish list. The virtualwish list device stores the details in the wish list along withidentifying information about the item. The virtual wish list devicestores some of the information to be viewable by the avatar or by otherparties. Thus, a virtual wish list device may assign access rights toothers and indicate which details are viewable by specific otheravatars, user accounts, companies and businesses, etc. The virtual wishlist device may also arrange the item in the wish list according to thedetails. For example, the virtual wish list device arranges the itemsaccording to the date the item was designated. It may also separate thewish list items by category or by degrees of desirability. Further, thevirtual wish list device shows some details on a wish list, but hidesother details as metadata that may be mined for marketing or othercommercial use.

In some embodiments, the operations may be performed in series, while inother embodiments, one or more of the operations may be performed inparallel. For example designating an item, as in block 406, could beperformed in parallel with determining details about the item, as inblock 408.

FIG. 5 is an example flow diagram illustrating using virtual wish listdetails. In FIG. 5, the flow 500 begins at processing block 502, where avirtual wish list device accesses a virtual wish list to obtain detailsabout a desired item. A virtual wish list device can access a wish listin different ways. In one example, the virtual wish list device accessesa database which stores details about the wish list. In another example,a virtual wish list device sends a notification message of an entry on awish list to an avatar's friend. The notification message includesdetails, such as a virtual landmark indicating a location, orcoordinates in the virtual universe, where the item may be purchased, ora teleport link to the item's location. The message could contain otherdetails that indentify the item, and include the avatars notes about theitem. The virtual wish list device could place the message directly intoa second avatar's inventory. Further, the virtual wish list deviceprovides access to user accounts, including company accounts forcompanies that want to access details about wish list items. Further,the virtual wish list may determine other avatars that own clones of thedesired item and provide those avatars with information about the item.

The flow 500 continues at processing block 504, where the virtual wishlist device processes a transaction using the details. For example, avirtual wish list device selects an item on the wish list. The item haslocation information, such as coordinates in the virtual universe, wherea copy of the virtual item may be purchased. The virtual wish listdevice transports an avatar to the location. The virtual wish listdevice conducts the purchase of the item and places the item in thepurchasing avatar's inventory. The virtual wish list device thentransfers the item from a purchasing avatar's inventory to the avatar'sinventory who desired the item. For instance, if the purchasing avatarpurchases an item based on a desiring avatar's wish list request, thewish list item has details pertaining to the desiring avatar. Hence, thevirtual wish list device presents a “transfer” operation, which thepurchasing avatar may select. The virtual wish list device processes thetransfer operation to transfer the item from the purchasing avatar'sinventory to the desiring avatar's inventory. The virtual wish listdevice also provides a message to the desiring avatar, which messageindicates information about the purchasing avatar. If the item isdesired as a real-world item outside of the virtual universe, thevirtual wish list device purchases a real-world version of the virtualitem and initiates the physical delivery of the real-world version.Shipping information may be obtained from the avatar's account or fromdetails about the item on the wish list.

In another example, a virtual wish list device presents information to amerchant account or other avatar (“merchant avatar”) that possesses thedesired item and wishes to sell it. The virtual wish list device couldconvey, per the merchant avatar's request, an advertisement or a couponto the avatar who desires the item. Alternatively, the virtual wish listdevice could gift the item to the avatar, per the merchant's request,and place the item in the avatar's inventory along with a note from themerchant expressing gratitude for being a valued customer. The gift of avirtual item is an excellent way of building commercial good will withinthe virtual universe. Likewise, the virtual wish list device may giftand initiate the delivery of items in the real world to build commercialgood will outside of the virtual universe.

In yet another example, the virtual wish list device may mine data fromwish lists in the virtual universe, analyze the data, and deliver theanalyzed data to subscribed accounts, such as businesses. For example,the virtual wish list device gathers information from a plurality ofwish lists that pertain to items a subscribed account markets or isinterested in marketing. The virtual wish list device analyzes the datato provide valuable commercial services and products, such as providingmarket research, promoting and distributing real-world goods, andorganizing product roll outs.

The virtual wish list device may also use wish list details and data forbartering items between avatars. The virtual wish list device may alsotransfer items from the virtual wish list into real-world wish lists.For example, an avatar may already own or possess an item in the virtualuniverse. However, the avatar may want to indicate on a real-world wishlist that the avatar agent wants the item in the real world.Consequently, the virtual wish list device may add the item, per theavatar's request, onto a real-world wish list.

Example Virtual Wish List Device Network

FIG. 6 is an illustration of a virtual wish list device 602 on a network600. In FIG. 6, the network 600, also referred to as a virtual wish listdevice network 600, includes a first local network 612 that includesnetwork devices 604 and 608 that may use the virtual wish list device602. Example network devices 604 and 608 may include personal computers,personal digital assistants, mobile telephones, mainframes,minicomputers, laptops, servers, or the like. In FIG. 6, some networkdevices 604 may be client devices (“clients”) that may work inconjunction with a server device 608 (“server”). Any one of the networkclients 604 and server 608 may be embodied as the computer systemdescribed in FIG. 7. A communications network 622 connects a secondlocal network 618 to the first local network 612. The second localnetwork 618 also includes client 624 and a server 628 that may use avirtual wish list device 606.

Still referring to FIG. 6, the communications network 612 may be a localarea network (LAN) or a wide area network (WAN). The communicationsnetwork 612 may include any suitable technology, such as Public SwitchedTelephone Network (PSTN), Ethernet, 802.11g, SONET, etc. For simplicity,the virtual wish list device network 600 shows only six clients 604, 624and two servers 608, 628 connected to the communications network 622. Inpractice, there may be a different number of clients and servers. Also,in some instances, a device may perform the functions of both a clientand a server. Additionally, the clients 604, 624 may connect to thecommunications network 622 and exchange data with other devices in theirrespective networks 612, 618 or other networks (not shown). In addition,the virtual wish list devices 602 and 606 may not be standalone devices.For example, the virtual wish list device 602 may be distributed acrossmultiple machines, perhaps including the server 608. The virtual wishlist device 602 may be embodied as hardware, software, or a combinationof hardware and software in a server, such as the server 608. One orboth of the virtual wish list devices 602 and 606 may also be embodiedin one or more client machines, possibly including one or more of theclients 604 and 624. For instance, servers may embody functionality(e.g., as code, a processing card, etc.) that searches for items thatlack details so that a virtual wish list device may prepare those itemsfor use with virtual wish lists. Functionality for designating virtualitems on virtual wish lists and processing transactions using virtualwish list details may be embodied in one or more server machines ordistributed as tasks to client machines accessing the virtual universe.For example, designating virtual items on wish lists may be performed asa background task on client machines distributed by servers.

Example Virtual Wish List Device Computer System

FIG. 7 is an illustration of a virtual wish list device computer system700. In FIG. 7, the virtual wish list device 700 (“computer system”)includes a CPU 702 connected to a system bus 704. The system bus 704 isconnected to a memory controller 706 (also called a north bridge), whichis connected to a main memory unit 708, AGP bus 710 and AGP video card712. The main memory unit 708 may include any suitable memory randomaccess memory (RAM), such as synchronous dynamic RAM, extended dataoutput RAM, etc.

In one embodiment, the computer system 700 includes a virtual wish listdevice 737. The virtual wish list device 737 may process communications,commands, or other information, to control and use virtual universe wishlists. The virtual wish list device 737 is shown connected to the systembus 704, however the virtual wish list device 737 could be connected toa different bus or device within the computer system 700. The virtualwish list device 737 may include software modules that utilize mainmemory 708. For instance, the virtual wish list device 737 may wholly orpartially be embodied as a program product in the main memory 708. Thevirtual wish list device 737 may be embodied as logic in the CPU 702and/or a co-processor, one of multiple cores in the CPU 702, etc.

An expansion bus 714 connects the memory controller 706 to aninput/output (I/O) controller 716 (also called a south bridge).According to embodiments, the expansion bus 714 may be include aperipheral component interconnect (PCI) bus, PCIX bus, PC Card bus,CardBus bus, InfiniBand bus, or an industry standard architecture (ISA)bus, etc.

The I/O controller is connected to a hard disk drive (HDD) 718, digitalversatile disk (DVD) 720, input device ports 724 (e.g., keyboard port,mouse port, and joystick port), parallel port 738, and a universalserial bus (USB) 722. The USB 722 is connected to a USB port 740. TheI/O controller 716 is also connected to an XD bus 726 and an ISA bus728. The ISA bus 728 is connected to an audio device port 736, while theXD bus 726 is connected to BIOS read only memory (ROM) 730.

In some embodiments, the computer system 700 may include additionalperipheral devices and/or more than one of each component shown in FIG.7. For example, in some embodiments, the computer system 700 may includemultiple external multiple CPUs 702. In some embodiments, any of thecomponents may be integrated or subdivided.

Any component of the computer system 700 may be implemented as hardware,firmware, and/or machine-readable media including instructions forperforming the operations described herein.

The described embodiments may be provided as a computer program product,or software, that may include a machine-readable medium having storedthereon instructions, which may be used to program a computer system (orother electronic device(s)) to perform a process according toembodiments of the invention(s), whether presently described or not,because every conceivable variation is not enumerated herein. A machinereadable medium includes any mechanism for storing or transmittinginformation in a form (e.g., software, processing application) readableby a machine (e.g., a computer). The machine-readable medium mayinclude, but is not limited to, magnetic storage medium (e.g., floppydiskette); optical storage medium (e.g., CD-ROM); magneto-opticalstorage medium; read only memory (ROM); random access memory (RAM);erasable programmable memory (e.g., EPROM and EEPROM); flash memory; orother types of medium suitable for storing electronic instructions. Inaddition, embodiments may be embodied in an electrical, optical,acoustical or other form of propagated signal (e.g., carrier waves,infrared signals, digital signals, etc.), or wireline, wireless, orother communications medium.

General

This detailed description refers to specific examples in the drawingsand illustrations. These examples are described in sufficient detail toenable those skilled in the art to practice the inventive subjectmatter. These examples also serve to illustrate how the inventivesubject matter may be applied to various purposes or embodiments.Although examples refer to items, services may be added to a wish list.For example, an avatar may select a salon store front to indicate adesire for a manicure or haircut. Other embodiments are included withinthe inventive subject matter, as logical, mechanical, electrical, andother changes may be made to the example embodiments described herein.Features of various embodiments described herein, however essential tothe example embodiments in which they are incorporated, do not limit theinventive subject matter as a whole, and any reference to the invention,its elements, operation, and application are not limiting as a whole,but serve only to define these example embodiments. This detaileddescription does not, therefore, limit embodiments of the invention,which are defined only by the appended claims. Each of the embodimentsdescribed herein are contemplated as falling within the inventivesubject matter, which is set forth in the following claims.

1. A method, comprising: determining an item in a virtual universe thatis a desired by an inhabitant in the virtual universe; designating theitem as a desired item in a wish list of the virtual universe;determining details about the desired item; and storing the detailsabout the desired item in the wish list.
 2. The method of claim 1,further comprising: accessing the wish list to obtain the details aboutthe desired item; and processing a transaction using the details.
 3. Themethod of claim 2, wherein processing a transaction comprises mining andanalyzing details from the wish list to generate market research.
 4. Themethod of claim 1, further comprising: designating a desired service inthe wish list; determining details about the service; and storingdetails about the service.
 5. The method of claim 1, further comprising:preparing the item with details for designating the item in the wishlist.
 6. The method of claim 1, wherein designating the item comprises:determining information about the desired item selected from a groupconsisting of identifying features of the virtual item and notationsmade by the inhabitant regarding the desired item, and storing theinformation in the wish list, wherein the wish list is in theinhabitant's inventory.
 7. The method of claim 1, wherein determiningdetails comprises determining information selected from a groupconsisting of a universally unique identifier of the virtual item, adatabase identification number associated with the virtual item, amanufacturer name that created the virtual item, a date that the desireditem is designated in the wish list, a characteristic of the item,coordinates of a virtual merchant that sells a copy of the desired item,the inhabitants's name, the image of an avatar belonging to theinhabitant, a mailing address of an agent associated with theinhabitant, and demographic information of an agent associated with theinhabitant.
 8. A system comprising: a machine configured to connect to acommunication network, the machine configured to process data in avirtual universe; and a virtual wish list device configured to connectto any one of the machine and the communication network, wherein thevirtual wish list device comprises a virtual item designator unitconfigured to designate a desired item in an inventory wish list of avirtual universe, and a virtual wish list data handler configured todetermine details about the desired item and store the details in thevirtual wish list.
 9. The system of claim 8, further comprising: avirtual inventory manager configured to access the virtual wish list toobtain details about the desired item; and a virtual wish listtransactions processor configured to process transactions using thedetails about the desired item.
 10. The system of claim 8, furthercomprising: a wish list designation rules store configured to storerules regarding designation of the desired item in the wish list; and avirtual universe authorization information store configured to accessand control virtual universe accounts.
 11. The system of claim 8,wherein the virtual wish list device is configured to prepare thedesired item with details for designating the desired item in the wishlist.
 12. One or more machine-readable media having instructions storedthereon, which when executed by a set of one or more processors causesthe set of one or more processors to perform operations that comprise:determining an item in a virtual universe that is a desired by aninhabitant in the virtual universe; designating the item as a desireditem in a wish list of the virtual universe; determining details aboutthe desired item; and storing the details about the desired item in thewish list.
 13. The machine-readable media of claim 12, wherein theoperations further comprise: accessing the wish list to obtain thedetails about the desired item; and processing a transaction using thedetails.
 14. The machine-readable media of claim 13, wherein theprocessing operation comprises performing an operation selected from agroup consisting of transporting an avatar of the inhabitant to amerchant, purchasing a copy of the desired item, transferring a copy ofthe desired virtual item to an inventory of the inhabitant, sending anotification message to the inhabitant that the desired item has beengiven to the inhabitant, sending an advertisement to the inhabitant ofthe desired item, purchasing a real-world representation of the desireditem, and initiating a physical delivery of a real-world representationof the desired item.
 15. The machine-readable media of claim 12, whereinthe operations further comprise: preparing the desired item with detailsfor designating the item in the wish list.
 16. The machine-readablemedia of claim 12, wherein the designating operation comprisesdetermining information about the desired item selected from a groupconsisting of identifying features of the desired item and notationsmade by the inhabitant regarding the desired item, and storing theinformation in the wish list.
 17. A method comprising: cloning a firstobject in a virtual universe to create a second object in the virtualuniverse; copying unique identification data from the first object,wherein the unique identification data distinguishes the first objectfrom all other objects in the virtual universe; and associating theunique identification data from the first object with the second object.18. The method of claim 17, wherein the unique identification data is auniversally unique identifier.
 19. The method of claim 17, furthercomprising: determining, from the first object, non-uniqueidentification data selected from a group consisting of one or morecharacteristics that define the appearance of the first object in thevirtual universe and metadata associated with the first object;searching the virtual universe using the non-unique data as searchcriteria to find a third object in the virtual universe with similarnon-unique identification data; analyzing the third object to determinedetails from the third object; and associating details form the thirdobject with the first object.
 20. The method of claim 17, furthercomprising: designating the second object in a wish list of the virtualuniverse using the unique identification data; storing the uniqueidentification data in the wish list; and processing a transaction usingthe unique identification data in the wish list.